Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add hub and conversion for AzureMachinePoolMachine #1799

Merged
merged 1 commit into from Oct 28, 2021

Conversation

devigned
Copy link
Contributor

@devigned devigned commented Oct 27, 2021

What type of PR is this?
/kind bug

What this PR does / why we need it:
This PR adds in conversion logic for AzureMachinePoolMachines. I think this was missed in the v1beta1 API introduction. Without this change, v1alpha4 AzureMachinePoolMachines will not be able to be converted to or from other API versions.

Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

TODOs:

  • squashed commits
  • includes documentation
  • adds unit tests

Release note:

Add conversion support for `AzureMachinePoolMachine` for v1alpha4 <=> v1beta1

@k8s-ci-robot k8s-ci-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. kind/bug Categorizes issue or PR as related to a bug. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Oct 27, 2021
@k8s-ci-robot k8s-ci-robot added area/provider/azure Issues or PRs related to azure provider sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Oct 27, 2021
@devigned
Copy link
Contributor Author

/retest

System machine pools not ready

@devigned
Copy link
Contributor Author

/retest

AMCP provisioned successfully, but the agent pools had no status and timed out. I feel like there might be a timing issue in the managed cluster creation flow. /cc @alexeldeib

@k8s-ci-robot
Copy link
Contributor

@devigned: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
pull-cluster-api-provider-azure-e2e-exp d6dbfaf link false /test pull-cluster-api-provider-azure-e2e-exp

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@devigned
Copy link
Contributor Author

/hold

Got 3 strikes with -exp job, and now I'm out. I'm going to run this test locally and see if I can root cause the issue.

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 27, 2021
@mboersma
Copy link
Contributor

Weird...the code looks good to me. This was an error I had just noticed and was starting to hunt for, so thanks for pouncing on it first.

@CecileRobertMichon
Copy link
Contributor

I suspect that the AKS test failures are unrelated to this PR. See this thread in Slack: https://kubernetes.slack.com/archives/CEX9HENG7/p1635262955037000?thread_ts=1632943680.223800&cid=CEX9HENG7

https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api-provider-azure#capz-periodic-capi-e2e-full-main

@CecileRobertMichon CecileRobertMichon added this to the v1.0 milestone Oct 28, 2021
@CecileRobertMichon
Copy link
Contributor

/hold cancel

As discussed in office hours, let's not gate this on the failing aks test as the failure is unrelated and aks clusters don't use AzureMachinePoolMachines. Test issue being addressed in #1800

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 28, 2021
"sigs.k8s.io/controller-runtime/pkg/conversion"
)

// ConvertTo converts this AzureMachinePoolMachine to the Hub version (v1beta1).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@devigned I believe you also need to add conversion from v1alpha3

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AzureMachinePoolMachines didn't exist in v1alpha3. They were introduced in v1alpha4.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, that's what I was missing. Thank you.

@CecileRobertMichon
Copy link
Contributor

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 28, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CecileRobertMichon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 28, 2021
@k8s-ci-robot k8s-ci-robot merged commit 4482f7f into kubernetes-sigs:main Oct 28, 2021
@k8s-ci-robot k8s-ci-robot removed this from the v1.0 milestone Oct 28, 2021
@k8s-ci-robot k8s-ci-robot added this to the v0.5 milestone Oct 28, 2021
@CecileRobertMichon CecileRobertMichon modified the milestones: v0.5, v1.0 Oct 28, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/provider/azure Issues or PRs related to azure provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/bug Categorizes issue or PR as related to a bug. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants